home *** CD-ROM | disk | FTP | other *** search
- Path: god.bel.alcatel.be!nlev00!barnhoorn
- From: barnhoorn@nlev00 ()
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Ceck out this bug. What the *** is SASC/6.56 doing?
- Date: 13 Mar 1996 11:22:31 GMT
- Organization: Alcatel Bell
- Distribution: world
- Message-ID: <4i6b5n$fiq@btmpjg.god.bel.alcatel.be>
- References: <1120.6643T91T406@login.eunet.no> <sassek.826554207@sas.com> <422.6645T351T2154@login.eunet.no>
- Reply-To: barnhoorn@nlev00 ()
- NNTP-Posting-Host: 138.203.178.61
- X-Newsreader: mxrn 6.18-10
-
-
- In article <422.6645T351T2154@login.eunet.no>, patrick.hanevold@login.eunet.no (Patrick Hanevold) writes:
- >
- >>You are probably running out of stack. With a standard 4k stack,
- >>after the prolog of main(), you only have 640 bytes of stack left.
- >>Apparently not enough for OpenScreenTags(). The program runs
- >>fine with a 20k stack.
- >
- >Guess stack check is bugged then. Hmm.. maby it doesnt work on SC's own
- >code.
- >
- Stack check is not bugged, you have to known what exactly is checked.
- SAS only knows the amount of stack you allocate in your function,
- not the amount of stack that is also used by the functions you call.
-
- --
- ---------------------------------------------------------------------------
- Jaco Barnhoorn barnie@xs4all.nl
- Software Test Engineer barnhoorn%nlev00@btmv56.se.bel.alcatel.be
- Alcatel Telecom Systems
- Rijswijk, The Netherlands
- ---------------------------------------------------------------------------
-